This change is a material change that impacts projects
going forward. We are changing from an enum to a
{major}.{minor} regex expression and bundling the
spec within a package for convenience.

We came to this determination because we needed a way
to better support upgrading the specification. This
enables us to be able to explicitly support new features
as well as potentially add any future breaking ones
with out breaking support across the ecosystem or
forcing upgrades

The new pattern places the specification and
builds the documentation from the json schema itself
vs having a separate spec.

The spec.md is then generated from the schema, so
minor.major versions are always compatible and it
is easy to validate the spec documents align with
the schema.